Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

System properties for debugging #91

Merged
merged 2 commits into from
Sep 18, 2024
Merged

Conversation

petebankhead
Copy link
Member

I fear it's ugly, but I'm finding it useful at the moment...

The following Groovy script

System.properties['instanseg.debug.tiles'] = 'true'

can help identify tiles that will be processed, by switching behavior to only show tiles (and not actually calling the prediction).

The purpose is to spot potential redundant calculations that we could remove. For example, in this image some tiles could be cropped - or even dropped entirely, because they only overlap a region that is already covered by at least one other tile.

image

Before this proposed change, I was hacking about in the code to try to visualize what was happening...

Using
```
System.properties['instanseg.debug.tiles'] = 'true'
```
can help identify tiles that will be processed, by switching behavior to only show tiles (and not actually calling the prediction).
@petebankhead
Copy link
Member Author

Rationale: The cost of a single tile prediction for an RGB image is relatively low, but for a whole slide image with many channels it can grow quite a bit - so I think it's worth trying to optimize tile selection further.

@petebankhead petebankhead merged commit a9676ce into qupath:main Sep 18, 2024
1 check passed
@petebankhead petebankhead deleted the debug-tiles branch September 18, 2024 10:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant